We use the alpha and beta tags when the release cannot yet be called stable.

Stability means the absence of bugs, the presence of tests and documentation, and the overall completion of all APIs.

Since the 4th version of the core hasn't been fully developed yet, we release it as alpha.

Granted you Owner rights

Ok, so for the purpose of the CI I think it makes sense to parse the version from package.json and extract the tag from it, right?
For example, for version 4.0.0-alpha.30, the alpha part should be parsed and used for the tag. I'd probably use the semver library for that

Yeah, it would be great!

@kobezzza I added the NPM_TOKEN secret and a step to extract the prerelease tag from the version in package.json. I'm not sure how to test it without actually triggering a release, though, so maybe we can test it with the next release?

Note: npm now requires tokens to have an expiration date, so the token I added expires in 1 year (15/04/2025). It will need to be updated then.

Great! But you still need to duplicate the MR branch in V4

Hi @aabounegm ! I talked to @kobezzza , and he said that this cool feature is not working. Could you please take a look at what's wrong? It would be great if you could also scale it to v4fire/client.

Hmm, seems I copied a similar workflow file I had somewhere else, but forgot to update the env var for Yarn. Should be fixed by ac41319, I'll wait till the next release to verify it works and then copy the workflow file to client